The ETL job RMB_STG_230_COUNTERPARTY in SAS^® Risk Management for Banking violates the integrity constraint of the Counterparty_Mart staging table by permitting multiple COUNTERPARTY_RK values. The problem can occur even if the data that is loaded in the source tables do conform to the integrity constraints of those tables.

This issue occurs because the ETL job RMB_INT_100_I_COUNTERPARTY does not sufficiently consider the case in which there are multiple instances of a counterparty for different VALID_FROM_DTTM and VALID_TO_DTTM time periods.

The workaround is to remove the condition "COUNTERPARTY.VALID_FROM_DTTM <= &run_date < COUNTERPARTY.VALID_TO_DTTM" from the join condition in SQL Join 2. Then insert a WHERE clause in the SQL join with the condition "COUNTERPARTY.VALID_FROM_DTTM <= &run_date < COUNTERPARTY.VALID_TO_DTTM". That is:

1. Open the job RMB_INT_100_I_COUNTERPARTY:
   
   
   
   
2. Insert a WHERE clause:
   
   
   
   
3. Remove the condition "COUNTERPARTY.VALID_FROM_DTTM <= &run_date < COUNTERPARTY.VALID_TO_DTTM" from the SQL Join:
   
   
   
   
4. Add the condition "COUNTERPARTY.VALID_FROM_DTTM <= &run_date < COUNTERPARTY.VALID_TO_DTTM to the WHERE clause:
   
   
   
   

Alternatively, you can insert a separate extract into the job stream that extracts a single date from the Counterparty table.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Risk Management for Banking	Microsoft® Windows® for x64	3.11		9.3 TS1M2
		Microsoft Windows 8 Enterprise 32-bit	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Microsoft Windows 8 Enterprise x64	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Microsoft Windows 8 Pro 32-bit	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Microsoft Windows 8 Pro x64	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Microsoft Windows 8.1 Enterprise 32-bit	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Microsoft Windows 8.1 Enterprise x64	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Microsoft Windows 8.1 Pro	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Microsoft Windows 8.1 Pro 32-bit	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Microsoft Windows Server 2003 Datacenter Edition	3.11		9.3 TS1M2
		Microsoft Windows Server 2003 Enterprise Edition	3.11		9.3 TS1M2
		Microsoft Windows Server 2003 Standard Edition	3.11		9.3 TS1M2
		Microsoft Windows Server 2003 for x64	3.11		9.3 TS1M2
		Microsoft Windows Server 2008	3.11		9.3 TS1M2
		Microsoft Windows Server 2008 R2	3.11		9.3 TS1M2
		Microsoft Windows Server 2008 for x64	3.11		9.3 TS1M2
		Microsoft Windows Server 2012 Datacenter	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Microsoft Windows Server 2012 R2 Datacenter	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Microsoft Windows Server 2012 R2 Std	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Microsoft Windows Server 2012 Std	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Microsoft Windows XP Professional	3.11		9.3 TS1M2
		Windows 7 Enterprise 32 bit	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Windows 7 Enterprise x64	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Windows 7 Home Premium 32 bit	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Windows 7 Home Premium x64	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Windows 7 Professional 32 bit	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Windows 7 Professional x64	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Windows 7 Ultimate 32 bit	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Windows 7 Ultimate x64	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Windows Vista	3.11		9.3 TS1M2
		Windows Vista for x64	3.11		9.3 TS1M2
		64-bit Enabled AIX	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		64-bit Enabled HP-UX	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		64-bit Enabled Solaris	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		HP-UX IPF	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Linux	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Linux for x64	3.11	3.2	9.3 TS1M2	9.4 TS1M2
		Solaris for x64	3.11	3.2	9.3 TS1M2	9.4 TS1M2

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

Type:	Problem Note
Priority:	medium

Date Modified:	2014-02-07 06:46:55
Date Created:	2013-10-24 13:13:09